Skip to content

Conversation

@mcollina
Copy link
Member

Summary

  • append caller stack traces for fetch errors without overwriting existing internal stacks
  • keep wrapper frames only when missing and avoid duplicate frames
  • relax stack trace tests to assert presence of internal fetch frames and caller context

Testing

  • npx borp -p "test/fetch/client-error-stack-trace.js"

@codecov-commenter
Copy link

Codecov Report

❌ Patch coverage is 92.00000% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 93.25%. Comparing base (4b36fef) to head (8c9188f).

Files with missing lines Patch % Lines
index.js 92.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4778      +/-   ##
==========================================
- Coverage   93.25%   93.25%   -0.01%     
==========================================
  Files         109      109              
  Lines       34001    34023      +22     
==========================================
+ Hits        31708    31727      +19     
- Misses       2293     2296       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mcollina mcollina merged commit 1edea72 into main Jan 29, 2026
35 of 37 checks passed
@mcollina mcollina deleted the fix-fetch-stack-trace-2331 branch January 29, 2026 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants